Skip to content

ci: Version Packages (rc) - #8219

Open
github-actions[bot] wants to merge 1 commit into
solid-router-v2-prefrom
changeset-release/solid-router-v2-pre
Open

ci: Version Packages (rc)#8219
github-actions[bot] wants to merge 1 commit into
solid-router-v2-prefrom
changeset-release/solid-router-v2-pre

Conversation

@github-actions

@github-actions github-actions Bot commented Sep 2, 2026

Copy link
Copy Markdown
Contributor

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to solid-router-v2-pre, this PR will be updated.

⚠️⚠️⚠️⚠️⚠️⚠️

solid-router-v2-pre is currently in pre mode so this branch has prereleases rather than normal releases. If you want to exit prereleases, run changeset pre exit on solid-router-v2-pre.

⚠️⚠️⚠️⚠️⚠️⚠️

Releases

@tanstack/solid-router@2.0.0-rc.5

Patch Changes

  • #8192 96f50d9 - Bump solid-js, @solidjs/web, and @solidjs/signals to ^2.0.0-rc.6 across the monorepo. rc.6 provides the named flight-data source API (registerFlightDataSource / two-argument subscribeFlightData) that the Start single-flight integration now requires; @tanstack/solid-start's peer floor moves to rc.6 accordingly.

  • #8192 96f50d9 - New loadFlightTarget helper (exported from @tanstack/solid-router/ssr/server): the router's half of a single-flight refresh. Given the mutation request's target href, it builds a router for that location, loads it, and returns the dehydrated payload for the tsr flight-data slice, so server collectors can refresh router state alongside other caches on the same mutation response.

  • #8213 b445b89 - Native SSR state transfer for Solid: router match state (loaderData, beforeLoad context, status, errors) now rides Solid's hydration registry under tsr: keys instead of a bespoke bootstrap script, deferred loaderData promises stream natively via seroval, the client primes router state from the registry in the Router constructor (before any render context, eliminating boot-time refetches and bootLoad-style workarounds), and RouterProvider owns the server-side router.load() dispatch so server entries no longer await it manually.

@tanstack/solid-router-devtools@2.0.0-rc.5

Patch Changes

  • #8192 96f50d9 - Bump solid-js, @solidjs/web, and @solidjs/signals to ^2.0.0-rc.6 across the monorepo. rc.6 provides the named flight-data source API (registerFlightDataSource / two-argument subscribeFlightData) that the Start single-flight integration now requires; @tanstack/solid-start's peer floor moves to rc.6 accordingly.

  • Updated dependencies [96f50d9, 96f50d9, b445b89]:

    • @tanstack/solid-router@2.0.0-rc.5

@tanstack/solid-router-ssr-query@2.0.0-rc.5

Patch Changes

  • #8192 96f50d9 - Bump solid-js, @solidjs/web, and @solidjs/signals to ^2.0.0-rc.6 across the monorepo. rc.6 provides the named flight-data source API (registerFlightDataSource / two-argument subscribeFlightData) that the Start single-flight integration now requires; @tanstack/solid-start's peer floor moves to rc.6 accordingly.

  • #8193 5a6935f - Deprecated: Solid Query's QueryClientProvider now carries the Router + Query SSR pairing natively (registry hydration, named single-flight sources, redirect handling via userland glue), so this integration package is no longer needed. See the README for the migration.

@tanstack/solid-start@2.0.0-rc.5

Patch Changes

  • #8192 96f50d9 - Bump solid-js, @solidjs/web, and @solidjs/signals to ^2.0.0-rc.6 across the monorepo. rc.6 provides the named flight-data source API (registerFlightDataSource / two-argument subscribeFlightData) that the Start single-flight integration now requires; @tanstack/solid-start's peer floor moves to rc.6 accordingly.

  • #8192 96f50d9 - Adopt Solid's multi-source single-flight protocol: the router's flight data (loader/match state, dehydrated data) registers under its own source id (tsr), so other caches' slices — e.g. solid-query's sq — coexist on the same mutation response instead of competing for a single consumer slot, and a user-supplied collectFlightData hook adds data alongside the router's rather than displacing it. Requires solid-js / @solidjs/web 2.0.0-rc.6+ (named flight-data sources).

  • Updated dependencies [96f50d9, 96f50d9, b445b89]:

    • @tanstack/solid-router@2.0.0-rc.5
    • @tanstack/solid-start-client@2.0.0-rc.5
    • @tanstack/solid-start-server@2.0.0-rc.5

@tanstack/solid-start-client@2.0.0-rc.5

Patch Changes

  • #8192 96f50d9 - Bump solid-js, @solidjs/web, and @solidjs/signals to ^2.0.0-rc.6 across the monorepo. rc.6 provides the named flight-data source API (registerFlightDataSource / two-argument subscribeFlightData) that the Start single-flight integration now requires; @tanstack/solid-start's peer floor moves to rc.6 accordingly.

  • Updated dependencies [96f50d9, 96f50d9, b445b89]:

    • @tanstack/solid-router@2.0.0-rc.5

@tanstack/solid-start-server@2.0.0-rc.5

Patch Changes

  • #8192 96f50d9 - Bump solid-js, @solidjs/web, and @solidjs/signals to ^2.0.0-rc.6 across the monorepo. rc.6 provides the named flight-data source API (registerFlightDataSource / two-argument subscribeFlightData) that the Start single-flight integration now requires; @tanstack/solid-start's peer floor moves to rc.6 accordingly.

  • Updated dependencies [96f50d9, 96f50d9, b445b89]:

    • @tanstack/solid-router@2.0.0-rc.5

@github-actions
github-actions Bot force-pushed the changeset-release/solid-router-v2-pre branch 2 times, most recently from aef78c8 to 5cff938 Compare September 2, 2026 23:56
@github-actions
github-actions Bot force-pushed the changeset-release/solid-router-v2-pre branch from 5cff938 to 6b569d8 Compare September 3, 2026 12:05
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants